Tech Arsenal 1/Tech Arsenal (Arsenal Computer).ISO/tek-05/netpak23.zip/NETPAK.DOC

Text File | 1992-10-06 | 23KB | 485 lines

      ╒═══════════════════════════════════════════════════════════════╕
      │                          NETPAK v2.3                          │
      │                                                               │
      │      A collection of programs for network administrators      │
      ╘═══════════════════════════════════════════════════════════════╛

Author: Robert Kirby (CNE Certified NetWare Engineer)
        The Houston Chip Channel
        Copyright (c) 1990-92

        Send 20$ to:
        The Houston Chip Channel
        23126 Willow Run
        Tomball, Tx 77375

        Contact me on Compuserve at user id 76620,2313.

  These programs are extremely helpful in easing the pains of network
  administration.

  The general utilities can be used on any network operating system
  although some are written specifically for Novell NetWare.

  These utilities are written in the spirit of automation and
  remote control, and by using them the method of manually passing out
  new/upgraded boot diskettes for network users can be minimized.

  This is shareware software, and the registration cost is a mere $20.
  Please register this software so that I can continue to develop
  software at rock-bottom prices.

  Disclaimer:  Use this software at your own risk.


Version/revision info:
3/20/92   NETPAK23   - ver 2.3 A2T ASCII to Telix utility added...

2/14/92   NETPAK22   - ver 2.2 nfoscr.exe added, NEWAUTO changed to NEWCFG

5/16/91   NETPAK20   - version 2.0 - enhancements to utilities and new
                                     utilities added...

8/16/90   NETPAK12   - modified NEWAUTO to have the power to append to the
                       autoexec.bat path statement.

8/12/90   NETPAK11   - modified STATUS program to remove the underbars
                       modified PHASER program to include more sounds

8/01/90   NETPAK10   - version 1.0

────────────────────────────────────────────────────────────────────────
A2T
────────────────────────────────────────────────────────────────────────

This is an ASCII to Telix dialing directory conversion utility.  The docs
are listed in a separate file called A2T.DOC.


────────────────────────────────────────────────────────────────────────
HOWBOUT 1.2
────────────────────────────────────────────────────────────────────────
Intro:
     This program is used quite extensively to dynamically build directories
     for users on the network.  This is done in situations where disk space
     might be an issue and rather than giving everyone on the network all
     the config files for every program, you can use HOWBOUT to give config
     files to only the users who go in.

Operation:
  a) HOWBOUT.EXE sets errorlevel to 0 if a drive or directory or file that
     you give as a command line parameter exists, and 1 if the drive or
     directory or file that you give as a command line parameter doesn't
     exist.  This beats having to use "IF EXIST" in a batch file because
     IF EXIST will hang up if there is some type of disk error such as an
     empty floppy diskette drive.

     I have found this little utility to be one of the most useful ones
     yet.  It allows me to dynamically build config subdirectories, so that
     batch files can check for the existance of files, drives, or subdirectories
     and create whatever is needed the first time into an application program.

  b) Also provided is a batchfile called WHATBOUT.BAT.  You can use this
     to test the action of HowBout, and see how it would work in your
     own batch files.

Syntax:
  HOWBOUT [drive][path][file]

  Note:
      HOWBOUT will check for the existance of a file or dir in the A:
      drive without hanging up with "abort/retry" if a diskette isn't
      inserted.  This is very useful for determining if a user on a
      network boots from an A: drive or a C: drive or either.  This is
      done by doing something like:

      howbout c:\command.com
      if errorlevel 1 goto ADRIVE
      call upgrade c:
      goto SKIP
      :ADRIVE
      call upgrade a:
      :SKIP

  Enhancements:
      HowBout 1.2 will now expand the program parameter in cases where a
      drive letter is given.  This is very useful in networking, when
      trying to shorten parameters.  Therefore if S: expanded is equal to
      s:\users\rkirby, to test for an autoexec.bat file at S: you
      could enter "howbout s:autoexec.bat" rather than the full path of
      "howbout s:\users\rkirby\autoexec.bat".

      If you do a "howbout *.*" in a directory that contains no
      subdirectories or files, howbout returns errorlevel 1, but if a
      file or subdirectory is found, howbout returns errorlevel 0.


────────────────────────────────────────────────────────────────────────
NEWCFG 1.3
────────────────────────────────────────────────────────────────────────
Intro:
  NewCFG is a program that will update an autoexec.bat file (or any text
  file) on a given line number for a given number of lines.  NEWCFG reads
  NEW.CFG for its information.  The program was written for administrators
  of networks who have to upgrade autoexec.bat/config.sys files of network
  users.  This can also be used by software developers to upgrade a users
  autoexec.bat/config.sys file.  Some experimentation with this program will
  show that it is very fast and powerful.

    The internet that I work in decided on a standard set of environment
  variables, with only one NODE environment variable being on the boot
  drive/diskette, which specified the system number of the PC (4 digit
  number).  This NODE environment variable calls a batch file located on the
  network that loads in the rest of the environment variables descibing
  that particular workstation.  This reduced having to edit the boot disks
  so much, and centralized the location of the different network
  configurations for easier management.  So, something like this is in the
  main system login batch file:

  if not exist g:\machine\%node%.bat goto nonode
     call g:\machine\%node%.bat
     goto skip
  :nonode
     call g:\machine\standard.bat
  :skip

    What this program did is update the autoexec.bat file of the users as
  they were logging in to the newer NODE system.  It removed all the old
  environment variables, and put in the new NODE environment variable
  based on the room number of the person logging into the network.  The
  users select their room number from a pop up list and the proper node
  number environment variable is written to their autoexec.bat file and
  the old variables are removed.  The NODE environment variable option
  can be bypassed, as explained in further detail below.

Syntax:
    NEWCFG.EXE will accept 3 parameters.  The 1st parameter is the name of
  the file you want to update and is required.  The 2nd and 3rd parameters
  are optional, they are the line number of the file that you want to begin
  adding new lines and the -N switch which turns on the NODE room number
  list display.  If the -N (or -P) parameter is left off, lines are added or
  removed from the given file without user intervention, and the list will
  not be seen and the special node variable will not be added to the file.
  If the line number parameter is left off then the new lines will be added
  starting at line number 2 of the file.

  NEWCFG [path]MYFILE [Linenumber] [preference options: -n,-p]

  [path]MYFILE :
    This is the name of a valid file to update.  This is a required
  parameter to NEWCFG.  If not given the program will terminate.  The
  validity (or existance) of the file can be tested with HOWBOUT.

  [Linenumber]
    This is an optional parameter which is the beginning line number to
  begin adding lines.  NEWCFG will begin adding new lines in the file in
  question beginning with this line number.  If left off, the default is 2.

  [preference options]
    -N,-n : If this parameter is given, the users will see the pop up
  scrollable list of room numbers.  The room numbers are tied to the
  system node numbers which are written to the file in question to
  complete the : SET NODE=  line in new.cfg.  This variable will
  always be added to the 1st line (the special line) in new.cfg.
    -P,-p : If this parameter is given, the users file in question will
  be searched for a line that contains : PATH= and the 1st line in
  new.cfg (the special line) will be appended to the path statement.
  In this instance, you would place something like : \mysub\subdir in
  the 1st input line of New.CFG and \mysub\subdir will be appended
  to the path statement.  Of course, if you have no path statement then
  the 1st valid line in new.cfg (the special line) will not be added
  to anything.
    If you give neither of the above parameters, the lines can be added
  and removed from the file in question, with no special significance
  placed on the 1st valid line in new.cfg.


  NEW.CFG :
    NEWCFG looks for a text file called NEW.CFG.  If this isn't found
  the program will terminate.  If NEW.CFG isn't in the current directory
  then the environment PATH will be searched.  First the lines to be added
  are read, then the lines to be deleted are read, the the node / room
  numbers are read.  Any lines that contain a semicolon in the 1st column
  or blank lines are completely ignored.
    You can place up to 20 new lines into someone's file and so you could
  have 20 lines to add.  These lines are terminated with a * delimiter in
  the first column of the following line.  The 1st line of the new lines
  listed in NEW.CFG is special, this is the line that the user-selected
  NODE variable is added to if the optional -N commandline switch is used.
  The is why this line will look like :  SET NODE=  if you are using the
  option -N switch.  Also note: the lines to be added are also DELETED from
  the file so that if a user makes a mistake, they can rerun the program
  and all previously added lines are deleted so they wont conflict with
  the new lines.
    Next, you can delete up to 20 lines from someone's file, so you can
  have 20 lines here.  These lines are also terminated with a * delimiter
  in the first column of the following line.  The strings that you give
  here must be an exact match, although they aren't case sensitive.  This
  is where old environment variables etc.. can be deleted.
    Next, if the optional -N commandline switch is used, a list of node
  numbers and room numbers are read.  This list is constructed into a
  user-selectable room number list, so the users choose from a list of
  room numbers and in the background the proper node number tied with the
  room number is added to the line "SET NODE=".  The four digit node system
  number is listed beginning in the 1st column and beginning in the
  5th column a room number is listed on each line for the number of nodes.
  Up to 255 nodes can be specified.  To change these parameters the source
  code can be easily modified, although having more than 255 nodes would
  also entail changing the source to the listttt5 unit in the Turbo
  Technojock's Toolkit.

Example:
  ;   this is a sample new.cfg file, the following are lines to add:
  ;   note these strings will also be deleted (for reruns of the program)
  ;   if they exist in the file already.  up to 20 lines can be added
  SET NODE=
  ECHO NODE %NODE% Booting into the Network...
  *
  ; lines to delete (up to 20 lines)
  SET GRAFCARD=VGA
  SET GRAFCARD=MONO
  SET GRAFCARD=EGA
  *
  ; node number <space> room number - the user selects the room number.
  ; up to 255 node number <space> room number lines.
  7205 1165A
  7206 1160
  7207 1163
  <eof>

  Enhancements:
  If you give a parameter of 1 for linenumber, NEWCFG assumes that you are
  not processing a batch file, but a text file.  If the 1 parameter is given
  for a linenumber then the preference options parameter should be left off.
  The 1 parameter is useful for placing titles at the top of text files.
  If the 1 parameter is given, it will only add a line to the top of the
  file.

  NewCFG will now automatically delete empty lines from files.  This is
  preferred when processing large text files.

  The figures of 10 lines to add and 10 lines to delete have been increased
  to 20.

────────────────────────────────────────────────────────────────────────
NFOSCR 1.0
────────────────────────────────────────────────────────────────────────
Purpose:
  NFOSCR.EXE will display a screen of useful network information.
  This information is Novell NetWork specific.  This will help out in
  getting information from a user over the phone.

Syntax:
  NFOSCR -p=help_desk_phone_number [%LOGIN_NAME] [*] [One line message]

  The program converts the command line parameters into either a one line
  or a screen full of network info.  To create the info screen, a '*' is
  inserted on the command line to separate the login name from the message.
  The login name is listed first.  A one line message is then listed that
  will be displayed at the bottom of the information screen.

  If the '*' is left off, then the message is displayed as a one line message.

Example:
NFOSCR RAKIRBY, * Enter LO to logout, LI to login, or GO to return to the menu.

────────────────────────────────────────────────────────────────────────
NWPRINT 1.0  NetWare Print Utility
────────────────────────────────────────────────────────────────────────
Purpose:
  This program is a front-end to the netware print command call NPRINT.
  It will allow you to quickly build a batch file that will send any
  number of print jobs to any number of print queues on the network.
  This was mainly written for CAD users to send batch plots at night
  to various queues, but it can be applied by anyone on the network.

Syntax:
  NWPRINT [path]outfile.bat [parameter 1-6]

    This program will display a screen of sequential data entry fields
  (mouse is supported).  First a network print queue list will pop up.
  You select a print queue from this list.  Next, you are asked whether
  you want to send output to the queue or view the status of the queue.

  Note, you will need a QLIST.EXE to view the status of a queue.  I did
  not write QLIST.EXE, and have no idea who did.  I found it on Compuserve
  (along with the source code) and found it to be useful in viewing the
  status of network queues in the NetWare environment.  You can find it
  there in the NetWare forums on Compuserve....

  If you want to view the status of the queue, this action will be taken
  and you will be asked if you want to continue.  If you want to send
  output to a queue, you will next be asked how many copies, and then
  a directory listing will display.  You then select a file entry from
  the directory.  This NPRINT line is then written to the file you specified
  on the command line.  You are then asked if you want to continue, if so,
  the queue list is displayed again.  In this way you can send any number
  of files to any number of network print queues.
    I have also included a batch file called NETPRINT.BAT that executes
  NWPRINT in a real world situation as an example of how NWPRINT can be
  used.

  [path]outfile.bat
    This is the printing batch file that is built with NWPRINT.  The
  entries of this file will be displayed at the bottom of the screen as
  they are created.

  [parameter 1-6]
    NWPRINT will accept 6 additional NPRINT parameters.  In other words,
  NWPRINT will accept the parameters that NPRINT accepts.  The copy and
  queue parameters are already inherent in the program execution.

  NWPRINT.CFG:
    This file is required.  It may either be with the program or it may
  be in your current directory.  This is so that everyone on the network
  can have their own nwprint.cfg file along with having a default (in case
  they don't have one) with the program.  NWPRINT.CFG is built in this way:

  i:\lib\*.*   {this is a filespec for your printing data directory}
  queue1       {these are the network print queues listed.
  queue2
  queue3
  queue4


────────────────────────────────────────────────────────────────────────
PHASER 1.1
────────────────────────────────────────────────────────────────────────
Purpose:
  This program is similar to the FIRE PHASERS command in the login script
  language of NetWare.  Sometimes it's fun to use those sort of sounds in
  a batch file also..  So this program was written.  PHASER has been
  expanded to include a hodge podge of sounds to make life on the network
  a little more interesting.  It is much more exciting that the typical
  batch file beep.

Syntax:
  PHASER [flavor] [# of times to fire] [ending pitch]

* Special Note: The order of the parameters has been changed!  If you are
  currently using an old version of Phaser please notice that the number
  of repetitions now comes 1st on the command line, and the frequency is
  the last of all.  If you don't update this, the user might end up with
  600 (or whatever) repetitions of Phaser!

  flavor :
    You can pick from 4 different flavors of sounds.  The default is the
    NetWare FIRE PHASER sound unless you give no parameter at all, then
    you will get the ordinary sounding beep.  The flavor parameter must
    be the first in the command line if it is there at all.  Here are
    the different sounds:

    -n : NetWare FIRE PHASERS (this is the default if other parameters
         are given on the command line, but a standard beep will sound
         if no parameters at all are given.)

    -w : Weird sound, sounds sort of like the opening sound to the DR. WHO
         show.

    -r : Random sound.  This one is best done with a very high pitch
         parameter.  This sounds like the SCI FI background computer bleeps.

    -b : And last but not least, the Bugs Bunny song.  This only only takes
         one parameter, that is pitch and number of times to play are ignored.
         It will only play once, once is enough!


  number of times to fire:
    this is the number of times to make the sound you pick.  (excluding the
    Bugs Bunny Song which only plays one time).  This parameter always
    comes before the pitch parameter.  If left off the default is 3 times.

  ending pitch:
    this is generally the last pitch of the sound that you pick.  The NetWare
    FIRE PHASERS sound and the Dr. WHO sound both descend in pitch until this
    pitch is given.  If left off the default is 50 Hz.

  examples:

    PHASER 3          = FIRE PHASERS 3 TIMES (ending at 50 Hz)
    PHASER            = Plain jane PC BEEP
    PHASER -w 3       = Make DR.WHO sound 3 times (ending at 50 Hz)
    PHASER -w 4 300   = Make DR.WHO sound 4 times (ending at 300 Hz)
    PHASER -r 2 3000  = Make random computer Bleeps for 2 durations
                        using 3000 Hz as a seed to the random generator
    PHASER -b         = feeble attempt at the bugs bunny song
    PHASER -n 3 400   = NetWare FIRE PHASERS 3 times (ending at 400 Hz)


────────────────────────────────────────────────────────────────────────
QUEST 1.1
────────────────────────────────────────────────────────────────────────
Purpose:
  This is a LAN questionnaire program.  When the boss said, "we need to hand
  out a questionnaire to get some feedback"..  I saw tons of paperwork in
  front of me.  With this program, not one piece of paper was used.

Improvements:
  The questionnaire has been improved by giving users the option of browsing
  the questions (and not writing to the response file).  If the username
  field is left blank, the user is considered to be browsing.  Writing to
  the response file only occurs when a particular response is answered.  If
  nothing is answered, nothing is written to the response file except
  the questions (when they are not browsing).  If they are browsing, nothing
  is written to the response file.

  You may now also give a path/filename for the response file.  In this way,
  you can have the program location in one directory and the response file
  that is created can be located in another directory.  This is for situations
  where you might desire to create some sort of dropbox.  If you do not give
  the response filename as a parameter to the program, then the program will
  default back to response.dat located in the current program directory.

How its done:
  The program reads a file called question.dat to get 8 questions that you
  will ask the network users.  The program then builds a file called
  response.dat that places their responses and names into the file.  The
  program performs a file lock on the response file so only one can update
  it at a time.  If someone else is in, the person will get a message telling
  them to try again later.  For this program to operate properly, the user must
  have the program directory as their current directory.

  There are 4 files that come into play:
  QUEST.EXE    --- the main program
  ACTIV.FLG    --- a little flag created when someone is in the program.
                   if someone reboots while filling out the questionnaire,
                   you might have to delete this flag.  It keeps several
                   people from writing to response.dat at once.  This
                   file isn't included in this archive since it is created.
  QUESTION.DAT --- This contains eight questions of your own design.
                   (only one line per question)
  RESPONSE.DAT --- This is the response file that is built (you may change
                   this name with the optional filename parameter)


────────────────────────────────────────────────────────────────────────
STATUS 1.1
────────────────────────────────────────────────────────────────────────
Purpose:
  STATUS.EXE will display a fancy message at the top of a screen.  This
  is for informing network users of the status of the current program
  they are trying to execute.  It writes to the screen extremely fast,
  and therefore beats having to use the "ECHO" command in batch files
  which is slow.  This had been modified to just take the place of the
  echo command in batch files.  (note: the previous version of NETPAK
  used UNDERBARS to designate spaces, but this was cumbersome so the
  program was updated to avoid the underbars).  Also the program has
  been tweaked a little to speed things up as fast as possible.

Syntax:
  STATUS [name of the application] [*] [status of current application]

  The program converts the command line parameters into either a one line
  or two line message.  To create a two line message, a '*' is inserted
  on the command line to separate the two messages.  The 1st message is
  the name of the application being executed and the 2nd message is the
  status of the application.  If the '*' is left off, then the message is
  displayed as a one line message.

Example:
   rem displays a 2 line message
   Status WordPerfect 5.1 Now Loading * Please be patient...
   rem displays a 1 line message
   status Enter LO to logout or GO to return to the network menu.